2013-05-20 - 4674.600 - Process Procedure - BW Initialization #SalesDistribution
PROCESS PROCEDURE
4674.600 - BW Initialization for Orders, Deliveries & Billing Documents
Summary Description
Need to re-initialize the BW datasources for Orders, Deliveries and Billing documents for updating the new Shipped source in NBP.
Admin Info
Title
|
BW Initialization
|
Requested by
|
Mark Harris
|
Created Date
|
05-20-2013
|
Approved by
|
Uday Kumar P
|
Approved Date
|
05-20-2013
|
Status
|
Complete
|
Detailed Description
The existing initialization requests in BW PSA tables were flushed out to increase the available database space. This resulted in Shipped Source not being able to be loaded with the Orders and Delivery information for the SH100 report requirement. Further a new field 'Bill of Lading' was added to the extract structure of delivery datasource 2LIS_12_VCITM. Hence the BW Datasources for Orders, Deliveries and Billing documents need to be initialized freshly with the data from NEP.
Process Flow & Navigational Steps
(Include Screen Shots if required)
Please refer the attached document below for the detailed Steps and Checklist involved in BW Initialization process:
Initialization Steps & Checklist 05-04-2013.pdf
Initialization Steps & Checklist 05-04-2013.doc
Please refer the attached document below for the Runtime statistics involved in BW Initialization process:
BW & ECC Initialization Runtimes 05-04-2013.pdf
BW & ECC Initialization Runtimes 05-04-2013.doc
Please refer the attached document below for the Runtime Datasheet used for BW Initialization process:
Initialization Runtime Datasheet 05-04-2013.pdf
Initialization Runtime Datasheet 05-04-2013.xlsx
Common Issues
The following issues were observed during BW initialization process:
1) Error documents - Some Billing documents have errors in NEP, that cause the Filling Job to fail while filling setup tables.
2) Invalid Dates - Some sales orders have invalid dates in NEP, that cause the Sales order and Service level DSO activations to fail.
3) Downtime Postings - During the NEP downtime when the setup tables are populated, some documents are posted in NEP that may cause some inconsistency.
4) Hash # values - Some deliveries were having the '#' values in Bill of Lading field, that caused the loading process to fail.
5) Multiple Parallel loads - When multiple parallel info packages were triggered, they caused the TRFC queues to be blocked slowing down the loading process.
Resolutions
For Issue 1 above - During the process of filling the Setup tables for billing documents, the value for number of faulty documents was given as 100 to prevent the job failure.
For Issue 2 above - Need to identify and fix the sales order dates in PSA tables, before loading them further into DSO object.
For Issue 3 above - All the documents that were posted during the downtime, were collected in a separate delta request so that they can later be overwritten using a full load.
For Issue 4 above - All the '#' values were edited in PSA table before updating to the Shipped DSO.
For Issue 5 above - Avoided triggering multiple info packages simultaneously and executed them in sequence.
Release Information
None